SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 40443: Metadata credentials do not pass to the server when using the SASCMD= option to start a multi-process SAS/CONNECT® (MP CONNECT) session

DetailsHotfixAboutRate It

When you use the SASCMD= option to start an MP CONNECT server session, the metadata credentials of the client are not passed to the server and it appears that the server does not respond. This problem is likely to occur with SAS® Enterprise Guide®, SAS® Enterprise MinerTM, and SAS® Data Integration Studio clients if these clients are not submitting to the grid and are doing multi-core processing on the same machine.

Currently, only metadata credentials are sent to an MP CONNECT server if the server was started using the SIGNON statement for the grid or the SERVER= option in the SIGNON statement.

As a workaround to ensure that the MP CONNECT session does NOT make a metadata connection, add the NOCONNECTMETACONNECTION option before the SIGNON statement that contains the SASCMD= option, as follows:

options sascmd="!sascmd" noconnectmetaconnection;

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS/CONNECTz/OS9.21_M29.39.2 TS2M39.3 TS1M0
Microsoft® Windows® for 64-Bit Itanium-based Systems9.21_M29.39.2 TS2M39.3 TS1M0
Microsoft Windows Server 2003 Datacenter 64-bit Edition9.21_M29.39.2 TS2M39.3 TS1M0
Microsoft Windows Server 2003 Enterprise 64-bit Edition9.21_M29.39.2 TS2M39.3 TS1M0
Microsoft Windows XP 64-bit Edition9.21_M29.39.2 TS2M39.3 TS1M0
Microsoft® Windows® for x649.21_M29.39.2 TS2M39.3 TS1M0
Microsoft Windows Server 2003 Datacenter Edition9.21_M29.39.2 TS2M39.3 TS1M0
Microsoft Windows Server 2003 Enterprise Edition9.21_M29.39.2 TS2M39.3 TS1M0
Microsoft Windows Server 2003 Standard Edition9.21_M29.39.2 TS2M39.3 TS1M0
Microsoft Windows Server 2003 for x649.21_M29.39.2 TS2M39.3 TS1M0
Microsoft Windows Server 20089.21_M29.39.2 TS2M39.3 TS1M0
Microsoft Windows Server 2008 for x649.21_M29.39.2 TS2M39.3 TS1M0
Microsoft Windows XP Professional9.21_M29.39.2 TS2M39.3 TS1M0
Windows 7 Enterprise 32 bit9.21_M29.39.2 TS2M39.3 TS1M0
Windows 7 Enterprise x649.21_M29.39.2 TS2M39.3 TS1M0
Windows 7 Home Premium 32 bit9.21_M29.39.2 TS2M39.3 TS1M0
Windows 7 Home Premium x649.21_M29.39.2 TS2M39.3 TS1M0
Windows 7 Professional 32 bit9.21_M29.39.2 TS2M39.3 TS1M0
Windows 7 Professional x649.21_M29.39.2 TS2M39.3 TS1M0
Windows 7 Ultimate 32 bit9.21_M29.39.2 TS2M39.3 TS1M0
Windows 7 Ultimate x649.21_M29.39.2 TS2M39.3 TS1M0
Windows Vista9.21_M29.39.2 TS2M39.3 TS1M0
Windows Vista for x649.21_M29.39.2 TS2M39.3 TS1M0
64-bit Enabled AIX9.21_M29.39.2 TS2M39.3 TS1M0
64-bit Enabled HP-UX9.21_M29.39.2 TS2M39.3 TS1M0
64-bit Enabled Solaris9.21_M29.39.2 TS2M39.3 TS1M0
HP-UX IPF9.21_M29.39.2 TS2M39.3 TS1M0
Linux9.21_M29.39.2 TS2M39.3 TS1M0
Linux for x649.21_M29.39.2 TS2M39.3 TS1M0
OpenVMS on HP Integrity9.21_M29.39.2 TS2M39.3 TS1M0
Solaris for x649.21_M29.39.2 TS2M39.3 TS1M0
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.